Release 10.1A: OpenEdge Development:
Progress Dynamics Administration

Creating a shortcut icon to start a session

To create a shortcut icon to start Progress Dynamics, you must specify startup parameters and properties that:

Specify the session type.
Specify the location of your configuration XML file.

Use the -icfparam startup parameter with the qualifiers described in Table 2–3.

Table 2–3: Qualifiers for the -icfparam startup parameter

Qualifier	Description	Default value
ICFCONFIG	Specifies the XML file to use for startup.	icfconfig.xml in your PROPATH.
ICFSESSTYPE	Specifies the session type.	Default session type.

Copying a shortcut

Use the Progress Dynamics shortcut icons as a starting point.

To copy shortcut icons:

Right-click the Dynamics Runtime icon from the Windows Start menu, then choose Copy from the pop-up menu.
Paste the copy of the icon on your desktop or wherever you want to create your new shortcut.
Right-click on the icon and choose the Rename pop-up menu option.

Setting up shortcuts that use a local configuration file

Once you have made a copy of a Progress Dynamics shortcut, you must edit the properties to specify the appropriate session type and configuration file. This is an example using a configuration file named dyncongif.xml, which was locally generated in your working directory.

To edit the properties of the shortcut:

Right-click and choose the Properties pop-up menu option.
In the Properties dialog box’s Target field, edit the values of the -icfparam startup parameter qualifiers. For example, if the session type you want to use is called MyAPP and your configuration file is called dynconfig.xml, use the following values:

-icfparam ICFSESSTYPE=MyAPP ICFCONFIG=dynconfig.xml

Edit the Start in field, if needed, as shown:



Choose OK.
To test to make sure your session configuration works, start the Repository database and your application database.
Double-click on your new shortcut.

Setting up shortcuts that use a remote configuration file

You can have shortcuts that access configuration files on remote machines as long as it is possible to use the Universal Naming Convention (UNC) to access resources on the remote machine.

To create a shortcut that uses a remote configuration file:

Copy your configuration file to the location on the network where you want to make it available.
Right-click and choose the Properties pop-up menu option for your shortcut.
In the Properties dialog box for the shortcut, edit the -icfparam startup parameter setting for dynconfig.xml to the full UNC path to the file on the network.

For example, if you copy the ICFCONFIG to a server called myserver on a share name called configurations in a directory called dynamics, the UNC share name is:

//myserver/configurations/dynamics/dynconfig.xml

You set the ICFCONFIG attribute of the -icfparam startup parameter to:

ICFCONFIG=//myserver/configurations/dynamics/dynconfig.xml

If you deploy the icfconfig.xml on the same server while the server is acting as the Web sever, set the ICFCONFIG attribute to:

ICFCONFIG=http://myserver/configurations/dynamics/dynconfig.xml